Skip to content

Conversation

@dennwc
Copy link

@dennwc dennwc commented Sep 19, 2022

Add non-portable key code to the key.Event type. This allows users to handle platform-specific key codes in the application code. Backends will now always generate input events, even for keys with no well-known names. Previously backends only generated events for keys they recognized.

Signed-off-by: Denys Smirnov [email protected]

Add non-portable key code to the key.Event type. This allows users to handle platform-specific key codes in the application code. Backends will now always generate input events, even for keys with no well-known names. Previously backends only generated events for keys they recognized.

Signed-off-by: Denys Smirnov <[email protected]>
@eliasnaur
Copy link
Contributor

AFAICT, this PR implements key.Events with empty Names for unknown/non-portable key presses. How do you propose a Gio program process these? Ideally, demonstrate with a test in the io/router package.

@inkeliz
Copy link
Contributor

inkeliz commented Sep 20, 2022

I think that change will also help me with gioui/gio-x#8, since gamepad inputs on Android seems to be sent as normal keypresses (far I remember). 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants